Skip to content

Add AGENTS.md with Cursor Cloud development instructions#37

Draft
bobdivx wants to merge 2 commits into
mainfrom
cursor/setup-agents-md-f344
Draft

Add AGENTS.md with Cursor Cloud development instructions#37
bobdivx wants to merge 2 commits into
mainfrom
cursor/setup-agents-md-f344

Conversation

@bobdivx
Copy link
Copy Markdown
Owner

@bobdivx bobdivx commented May 16, 2026

Summary

Adds AGENTS.md with Cursor Cloud specific instructions for future agents working on this codebase.

What's included

  • Stack overview (Astro 6 SSR + Preact + Tailwind/DaisyUI)
  • Key development commands (npm install, npm run dev, npm run build)
  • Development notes and gotchas:
    • No ESLint/Prettier/test framework configured; build is the primary validation
    • astro check may hang in constrained environments
    • SQLite DB auto-creates on first dev server start
    • Auth flow: register at /login → setup wizard at /setup → dashboard
    • OpenClaw/Ollama/Docker are optional and gracefully degrade

Environment setup verified

  • Update script: npm install
  • Dev server: npm run dev on port 4321
  • Build: npm run build completes successfully

Demo

devforge_registration_and_dashboard_demo.mp4

Registration flow and dashboard navigation demo.

Dashboard overview
Agents management page
Projects page

To show artifacts inline, enable in settings.

Open in Web Open in Cursor 

Co-authored-by: Mathieu JESER <bobdivx@users.noreply.github.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 16, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
forge Ready Ready Preview, Comment May 16, 2026 9:49am

Co-authored-by: Mathieu JESER <bobdivx@users.noreply.github.com>
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces AGENTS.md, a documentation file detailing the project's tech stack, commands, and development workflows for the Forge dashboard. The review feedback identifies a maintainability risk due to the lack of linting and testing frameworks and points out a discrepancy between the documented behavior of the Docker API endpoint and its actual implementation.

Comment thread AGENTS.md

### Development notes

- **No ESLint/Prettier/test framework** is configured in this repo. The build (`npm run build`) is the primary correctness check.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The absence of ESLint, Prettier, and a testing framework is a significant maintainability risk.\n\nWhile documenting this state is helpful for agents, it highlights a major gap in the project's quality assurance. Relying solely on the build process for correctness checks can lead to regressions and inconsistent code style. It is highly recommended to integrate these tools to automate quality checks and ensure long-term project health.

Comment thread AGENTS.md
- The dev server auto-creates the SQLite database and seeds it on first run. No manual DB setup is needed.
- The app redirects unauthenticated users to `/login`. Register via the "Créer un compte" tab (min 10-char password). After registration, the setup wizard at `/setup` can be skipped.
- **OpenClaw** and **Ollama** are optional external services. The dashboard gracefully degrades when they are unreachable.
- The Docker-related API endpoint (`/api/docker.ts`) gracefully returns empty data when Docker is unavailable.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There is a discrepancy between this documentation and the implementation in src/pages/api/docker.ts.\n\nThe documentation states the endpoint "gracefully returns empty data when Docker is unavailable," but the code returns a 500 Internal Server Error if the docker command fails (e.g., if Docker is not installed or the daemon is not running). To achieve the documented "graceful degradation," the API should return an empty array [] with a 200 OK status on failure. If the current error behavior is intended, please update this documentation to reflect it.

Suggested change
- The Docker-related API endpoint (`/api/docker.ts`) gracefully returns empty data when Docker is unavailable.
- The Docker-related API endpoint (/api/docker.ts) returns an error response when Docker is unavailable (except on Vercel where it returns empty data).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants